Skip to content
This repository was archived by the owner on Jul 20, 2026. It is now read-only.

refactor(slack): 응답 계층 예시를 다양화한다#32

Merged
lbox-limit merged 1 commit into
mainfrom
codex/slack-response-hierarchy-examples
Jul 14, 2026
Merged

refactor(slack): 응답 계층 예시를 다양화한다#32
lbox-limit merged 1 commit into
mainfrom
codex/slack-response-hierarchy-examples

Conversation

@lbox-limit

Copy link
Copy Markdown
Collaborator

Type of Change

  • Feature skill - adds a channel or integration (source code changes + SKILL.md)
  • Utility skill - adds a standalone tool (code files in .claude/skills/<name>/, no source changes)
  • Operational/container skill - adds a workflow or agent skill (SKILL.md only, no source changes)
  • Fix - bug fix or security fix to source code
  • Simplification - reduces or simplifies source code
  • Documentation - docs, README, or CONTRIBUTING changes only

Description

Slack 응답 형식이 단일 상태 목록 예시의 ✅ + 굵은 label 표면 형태를 반복하던 문제를 개선합니다.

해설형 통제를 최소 계약으로 압축하고, 단문·공통 판정·혼합 상태뿐 아니라 코드 검토, 설계 선택, 장애 복구, 배포 준비도처럼 복잡한 정보를 상위 판정 → 역할별 묶음 → 한 단계 낮은 근거로 정리하는 예시를 추가했습니다. 상시 지침과 계약 테스트도 같은 계층 원칙을 유지하도록 갱신했습니다.

사용자는 간단한 답은 짧게 받고, 복잡한 결과는 결론과 판단 기준을 먼저 본 뒤 필요한 근거만 하위 계층이나 링크·파일에서 확인할 수 있습니다.

검증:

  • pnpm exec vitest run setup/provider-contract.test.ts — 22 tests passed
  • pnpm exec prettier --check container/skills/slack-formatting/SKILL.md container/skills/slack-formatting/instructions.md setup/provider-contract.test.ts
  • git diff --check

For Skills

  • SKILL.md contains instructions, not inline code (code goes in separate files)
  • SKILL.md is under 500 lines
  • I tested this skill on a fresh clone

@lbox-limit
lbox-limit marked this pull request as ready for review July 14, 2026 18:54
@lbox-limit
lbox-limit merged commit 1a24bff into main Jul 14, 2026
2 checks passed
@lbox-limit
lbox-limit deleted the codex/slack-response-hierarchy-examples branch July 14, 2026 18:54
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants